It could be an issue with the builtin VNC server. You can try to disable the Enable capturing of layered windows option in the service / VNC server options. Altering the other options could be worth a try as well. Which update interval have you configured on the master side?

Yes there should be no limit if you have enough RAM, see http://docs.veyon.io/en/latest/admin/installation.html#hardware-and-software-requirements for details. If you encounter CPU usage issues you can increase the thumbnail update interval in the configuration.

So, to make sure I understand correctly, an incremental upgrade is ok? Like, I can install 4.1.3 to the master, but not to the clients and it will be ok? Does 4.1.3 need to ever be installed to the clients for any improvement?

Thanks!

Hi everyone,

It a painful, but i manage to get my keyboard back. It wasn't working in safe mode, I try the repair option, it took some times but my laptop is working again. I haven't get the chance to re-install Veyon on it because it start working just in time for class. I'll try to "clean" the laptop before trying to re-install Veyon.

Thanks again for the help.

3 hours later I can confirm that the laptop is working as a charm and I was able to install Veyon on it.

Hi Toby,

Thanks for your reply, but I feel stupid, I was using the veyon-ctl command to reset config within a regular Command Prompt window ... (I still don't get why I need admin privilege when I'm already admin). Opening a Command Prompt as Administrator was what I've miss earlier to reset the config and push the new one.

All your suggestion were done it was Windows that trick me (again)

Sorry for the useless noise.

and thanks again for your reply.

You can use the silent installation method as described at https://docs.veyon.io/en/4.1/admin/installation.html#automated-installation-silent-installation

Still unable to solve the problem. it should be noted that this problem happens on windows 10

Thanks for reporting this issue. We'll add the missing code for disabling power saving mechanisms.

The same question has been answered at https://veyon.nodebb.com/topic/132/ldap-computers already 😉

This is a known bug and discussed in https://veyon.nodebb.com/topic/100/broadcasting-and-screen-lock/7 already. We're working on a solution and hope to get this fixed in 4.1.3.

Did you enable this option on clients and restarted the service and/or computer afterwards?

It was probably a temporary outage at readthedocs.org - works normally now.

Can you try to set the log level to "debug" in Veyon Configurator and run "veyon-server" programm manually in a terminal on the affected client? May be the server crashes or there's some kind of timeout issue.

Thank you for your investigations! I opened an issue at https://github.com/veyon/veyon/issues/420 so we can do further investigations and finally fix the issue.

Do the integration tests report computer rooms and computers properly? If so, did you change the network object directory to "LDAP/AD"? (https://docs.veyon.io/en/latest/admin/ldap.html#using-ldap-backends)

Thanks for reporting! Veyon 4.1.3 will include a fix which trims spaces and newlines from host and MAC addresses automatically when editing them through Veyon Configurator.

Sorry for the delay of the Ubuntu packages.

Hello @joffrey
welcome to Veyon! Remote login is currently not implemented but is planned for future releases, likely in 2019.